|
 |
>> I doubt that was *ever* the "recommended" way. And yet I, a person who
>> doesn't know C very well, am aware of this example. What does that
>> tell you? ;-)
>
> That you're looking for examples of why the language is incomprehensible.
Doesn't take much looking, does it?
> That you had a bad lecturer/textbook at university.
The long and short is, I spent several months at college using C, and I
always round it excrusiatingly difficult to get any of the programs to
work properly. Unfortunately that's just the way C is designed; nothing
is checked, the programmer is assumed to know exactly what they're
doing, and if the programmer does something wrong... well that's just
too bad.
I'm sure this makes the compiler much easier to implement, and no doubt
it contributes to the efficiency and flexibility of the language, but...
I prefer having some kind of safety features in a programming langauge.
> That you're reading up on why C++ is bad and what constructs are known
> to cause problems.
Actually... no.
> Taking the example to my prefered language, I'd say that 80% of people
> who have worked much with SQL can and will use cursors, yet every expert
> in SQL will tell people to never use them.
> Does that mean that SQL is incomprehensible to the average person and a
> language that's easy to break things in?
I guess it depends what you're trying to do. SQL certainly has a few
known flaws (default column orderings, anyone?), but in general it makes
it quite simple and easy to do most things.
In C, just concatinating two strings is an ugly, complex operation. In
fact, it seems to be easier to just write one string to stdout and then
write the other, rather than trying to actually concatinate them. The
language seems to make every tiny little operation really awkward and
difficult. No thanks...
Still, since I am the *only* person on the entire news server who thinks
this, I guess I should just let it go.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
